-
Notifications
You must be signed in to change notification settings - Fork 5.9k
open websocket on same path as page #149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This is the critical piece to let you serve code-server proxied under a path. Otherwise if you proxy e.g. `/editor/` thru to `http://localhost:8000`, everything works fine except the websocket connection is still opened to `/`
The app with this works minimally when proxied. There are some 404ing assets, which I'm not immediately sure how to fix:
Basically all of those should be |
Did these assets 404 prior to the WebSocket fix? |
The only one I can confirm is |
This issue fixed: |
* upstream/master: (35 commits) Dockerfile: use relative path instead of $PWD for CMD Update docker oneliner and fix clone task Clone exact vscode release branch when build task (coder#167) Add -t flag to docker example (coder#181) Reverts parts of my last PR (coder#177) Fix build and Dockerfile issues (coder#176) Add nginx reverse proxy guide for selfhosted Use a timing-safe equality check for passwords (coder#133) Open websocket on same path as page (coder#149) Adhere to XDG base directory spec for dataDir and logDir (coder#156) Improve github issue template (coder#162) Fix typo: environemnt -> environment (coder#159) Add back web class Move upx compression behind an env flag ci: enable travis npm cache (coder#110) Improve .dockerignore (coder#111) Feature/1.32.0 update (coder#117) Update grammar on README (coder#139) inital -> initial (coder#135) Handle arch in dockerfile and add PR template (coder#109) ...
This is the critical piece to let you serve code-server proxied under a path. Otherwise if you proxy e.g. `/editor/` thru to `http://localhost:8000`, everything works fine except the websocket connection is still opened to `/`
This is the critical piece to let you serve code-server proxied under a
path. Otherwise if you proxy e.g.
/editor/
thru tohttp://localhost:8000
, everything works fine except the websocketconnection is still opened to
/